An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hello, All of my submissions across my account have been stuck in review for many weeks, which is well outside my normal turnaround. These are apps that have historically been approved within 24 hours or 2-3 days. Those updates are time critical. Singapore MRT just updated on 12 July. We are losing installs and impressions largely because of this, especially no reason is given. App: Singapore MRT Map Route Apple ID: 536957287 / Version: 3.0.1 App: Singapore MRT Map Route(Pro) Apple ID: 475976737 / Version: 3.0.0 App: Epic Cards Battle Apple ID: 1003611640/ Version: 2.6.3 On my side everything appears complete: metadata, build, review notes, demo account credentials, and all agreements in Agreements, Tax, and Banking are accepted. There are no messages in Resolution Center and App Store Connect shows no action required from me. I have contacted Developer Support but have not received a actual response. Could someone please confirm whether these submissions are correctly queued, or whether something is blocking them that requires action on my side? Thank you.

We have an app that is updated regularly, and our submissions are typically reviewed within a few hours to one day. We recently submitted an urgent bug fix for a production issue affecting our customers. However, this submission has been stuck in "Waiting for Review" for the past 10 days without any updates. We've opened multiple support tickets, but they've led nowhere. Phone support has also been ineffective, with scheduled callbacks resulting in hours on hold without any progress. What is the appropriate escalation path for a submission that appears to be stalled in the review queue?

My app is in "Waiting for Review" for more than 7 days. I have contacted Apple Review team three times by email but no response from their side! The submission ID is: 9d476f53-4195-4143-985a-cb86ee1292fa For how long I should wait until the app gets reviewed?

I did not work hard for that new record, and neither did the Apple review team. :) A 10-year-old app with a large number of active users, and the update is just a simple bug fix. It has now been over a month since the original submission. This is a prayer times app. A bug in it affects thousands of people’s daily worship—wrong times, missed prayers. This is not a joke, and it is not a cosmetic issue that can sit in a queue for a month. Expedited review requests, the Contact Us form, and phone support have all produced nothing. If anyone from Apple is reading this: please review this submission—891c1b55-f353-4bf8-bb81-609b1c29a5cc.

I submitted my IOS app (Apple ID 6783073058) on 2026-07-21. The submission confirmation email says: On average, 50 percent of apps are reviewed in 24 hours and over 90 percent are reviewed in 48 hours. Once we've completed the review, your app's status will be updated and you will be notified. After 6 days still Waiting for Review, I asked Claude if there was any way to check on the status. He suggested opening a support ticket. When I filed 20000121192005 I was given the option to call or email, so I opted for a call. Immediately the phone rang. Then I sat on hold for 2 hours waiting to be connected. After that, I gave up and hung up. Immediately the phone rang again, but then told me that I had called Apple outside of business hours and hung up. I am a first time submitter, and have all kinds of questions about the submission process. If I did something wrong, please tell me so I can fix it. But leaving me in the queue for a week is just mean. Can I get a review, please?

I'm stuck on what looks like a backend / account-level TestFlight issue and want to ask if anyone has seen the same pattern. Symptoms (reproduced across three consecutive builds) App Store Connect ingests and processes each build successfully; it shows as "Testing" in TestFlight with no compliance warnings. Internal TestFlight install fails instantly on every tester device with: ▎ "The requested app is not available or does not exist." Device console (itunesstored) at install time: FAILED: TFBundleInstallation serverFailureReason="Error Downloading Install Data" userFailureReason="Requested app not available or does not exist" buildGroup=(null) phase=Failed previousPhaseDescription=ProcessingInstallInitiateResponse serverCode 200 Submitting the same build for external Beta App Review returns: 422 ENTITY_UNPROCESSABLE code: BETA_CONTRACT_MISSING buildGroup=(null) for builds that visibly show as "Testing", plus a persistent BETA_CONTRACT_MISSING, suggests the beta-contract / build-group record for the app is missing or corrupted on the backend. Already verified clean on the developer side Distribution certificate and provisioning profile valid; entitlements match the binary; codesign --verify --deep --strict passes. Free and Paid Apps Agreements both Active; no pending tasks (Banking, Tax complete). App Information, Pricing & Availability, Age Rating, Content Rights, Test Information all complete; build page shows no warnings. Reproduced with multiple testers on multiple iOS 17+ devices, in a fresh internal testing group, after device-side cleanup (sign-out / reinstall TestFlight). Re-uploading a fresh build does not clear it — so it is not bound to a specific binary. Questions Has anyone seen Error Downloading Install Data + buildGroup=(null) + BETA_CONTRACT_MISSING together on a single app? How did you resolve it? 2. Why does ProcessingInstallInitiateResponse return serverCode 200 while still failing with "app not available", for a build that shows as "Testing"? 3. Is there a documented path to request that engineering regenerate a corrupted beta-contract / build-group record, beyond a standard support case? Any pointers appreciated — happy to share device logs / sysdiagnose if useful.

please help me!

i sent my app for review over since 07/25 and it still "waiting for review" it feels like im abandon and no reply on emails through contact us. maybe someone know what is going on??? please help me my game name is LifePath: Life Simulator

I'm hoping someone here has navigated something similar or can point me to the right channel. My Apple Developer Program membership was terminated, with the notice citing Section 3.2(f) of the ADP Agreement and referring to indications of fraudulent conduct. No specific reason was given. As far as I can tell, the only significant change to my account beforehand was updating my country/region after I relocated. I did this openly through Developer Support: I disclosed the change, Apple asked me to verify my new address, I uploaded a government-accepted document, and a Developer Support agent confirmed Apple had reviewed it and updated my account so I could renew. So the location details on my account are accurate and were verified by Apple itself - which is why the "misrepresentation" framing is confusing to me. Two questions: What is the correct channel to formally appeal or request a review of an account termination? The "file a complaint under a Platform Regulation" link is not available in my region, and the general contact forms do not seem built for this. Has anyone here gone through a 3.2(f) termination and had it reviewed or reversed? What actually worked - phone support, a specific form, persistence? I'm trying to resolve this factually and in good faith. Any guidance is appreciated.

Hey people, I would like to know how long it usually takes a first-time app publisher to get their app reviewed for the first time. I submitted my app on 20.07.22026 and am still stuck waiting for a review status, and today is the 8th day in the queue. App is submitted from account 6783418786. • Is there a specific reason for this extended hold? • Is any action required from my side? • When can I expect the review to proceed? Thank you very much for your time and assistance.

Hello Team, I have submitted the app to get the app reviewed and release. In past it usually take 2 days to do the review the app . I have submitted my app on 21.07.22026 and am still stuck waiting for a review status, and today is the 8th day in the queue. App is submitted from account 6448613553. Thank you very much for your time and assistance.Please do let us know if I need to something on my end .

My app was rejected July 16 under Guideline 2.1 (Information Needed) with four questions about the Clinical Health Records API. I replied in full the same day in the Resolution Center, and followed up in that thread on July 22. It has now been 12 days with no response from App Review. I have also contacted Developer Support (case 102942988807), which replied twice but could not provide status on the submission. I have not clicked Resubmit, since Apple's message asked me to reply, and I understand resubmitting closes the correspondence thread. Is there anything further I should be doing, or is a reply alone sufficient to return the submission to the review queue? Submission ID: bc855e56-3ef8-482d-96b0-4380d3fc4a68

Hello Apple Developer Community, My Apple Developer Program membership was terminated under Section 3.2(f), citing “documented indications of fraudulent conduct associated with my account.” However, the termination notice did not identify any specific activity, app version, date, transaction, device, account association, or policy issue that led to this decision. WritePad is a legitimate social reading and writing platform with approximately 10,000 users and a 4.6 App Store rating. The application has been available on both iOS and Android and has undergone numerous successful App Review submissions. Before this termination, I had not received any warning or allegation of fraudulent or dishonest conduct. To the best of my knowledge, I have not knowingly engaged in or authorized fraudulent, dishonest, manipulative, or misleading activity involving App Review, ratings, reviews, downloads, payments, TestFlight, or Apple’s distribution services. I have already submitted a formal reinstatement petition to the App Review Board and received confirmation that my request was submitted. I understand that account-specific matters cannot necessarily be resolved publicly. However, I would appreciate guidance from Apple Staff regarding whether there is any additional official channel, documentation, or action I should use while the reinstatement request is being reviewed. I would also appreciate hearing from developers who received the same Section 3.2(f) termination notice: How long did the reinstatement review take? Did Apple request additional information? Was the specific reason ever explained? Was your account eventually reinstated? Thank you.

Our first app submission has been in "Waiting for Review" since July 23, 2026 and has not yet moved to "In Review" — now over five days with no communication in Resolution Center. App: UNA: Reflect & Remember (Apple ID 6757480598) Platform: iOS · Version 1.0 (build 201) Our App Review information is complete: an active demo account, detailed review notes, and a full walkthrough video are all attached. We're not looking to jump the queue — we'd just appreciate any insight into whether the submission is healthy and simply waiting on backlog, or whether anything is needed from our side. Are others seeing similar first-submission wait times right now? Thank you.

Our app sells two auto-renewable subscriptions. Product loading succeeds and returns both products with correct localized prices, but every purchase attempt fails roughly one second later with "Item Unavailable". No purchase sheet is ever presented to the user. The app has not yet passed its first App Review. It was rejected under Guideline 2.1(b) because the reviewer encountered this same error on their device. MY QUESTION Under what conditions does StoreKit reject a purchase with "Item Unavailable" for a product that has just been returned successfully, with a valid localized price, by a product request? Is an auto-renewable subscription transactable in the sandbox environment for an app that has never had a binary approved by App Review? Question 2 is the one I most need answered. App Review's rejection states that In-App Purchase products "do not need prior approval to function in review", but neither we nor the reviewer can transact them. DIAGNOSTIC LOG Captured on-device during a failing session: 01:08:56 fetchProducts [com.aurascanner.app.pro.weekly, com.aurascanner.app.pro.annual] 01:08:56 fetchProducts -> 2 product(s): com.aurascanner.app.pro.annual=$39.99; com.aurascanner.app.pro.weekly=$6.99 01:08:56 requestPurchase sku=com.aurascanner.app.pro.weekly 01:08:57 purchaseError: code=purchase-error msg=Item Unavailable 01:08:57 error code=purchase-error, storefront=USA 01:09:05 fetchProducts -> 2 product(s), same prices returned again 01:09:05 requestPurchase sku=com.aurascanner.app.pro.annual 01:09:06 requestPurchase threw: Item Unavailable 01:09:06 error code=purchase-error, storefront=USA An introductory-offer eligibility check earlier in the session also succeeded, using the subscription group ID read from the loaded product. So product metadata, including the subscription group, resolves correctly. CONDITIONS Fails identically for both products, on every attempt. Reproduces in TestFlight on our own devices and Apple IDs. Also failed during App Review on iPad Air 11-inch (M3), iPadOS 26.5.2. Storefront reports as USA in every case. Real devices only. Not reproduced on Simulator. ALREADY VERIFIED Paid Applications Agreement: Active, banking and tax information complete. In-App Purchase capability: enabled on the App ID at Certificates, Identifiers & Profiles. Bundle identifier com.aurascanner.app matches the App Store Connect record. Both subscriptions: complete metadata, review screenshots uploaded, USD pricing set, United States availability. Both subscriptions and the subscription group are attached to the current submission, status "Ready for Review". Subscription group has a localized display name. Build distributed via TestFlight, which routes purchases to sandbox automatically. IMPLEMENTATION The app is React Native and uses a wrapper library over StoreKit 2, but the error text originates from StoreKit rather than the wrapper, and the call order follows the documented pattern: Initialize the StoreKit connection. Load products. This succeeds and returns both products. Register transaction update and error listeners. Request the purchase. This is where it fails. Purchases are verified server-side using Apple's App Store Server Library, and the transaction is finished only after verification succeeds. I am not asking anyone to debug the wrapper. My question is about StoreKit and App Store behaviour: what causes the store to quote a product and then decline to sell it? Any pointers appreciated. I can supply screenshots or the full log.

Hello, Our first app submission has been in "Waiting for Review" since July 22 with no status change (6 days). App name: Randevu Sıram Bundle ID: com.siram.app Version / Build: 1.0 (19) Submission ID: 8499a973-8efa-4066-bb5c-e28847a07e34 Date submitted: July 22, 2026, 12:21 PM Support Case ID: 20000120821151 This is our first submission from a new developer account. The App Review Information section includes a demo account for the business panel, and the customer side is usable without login. We contacted App Review Support on July 26 (case above) but have not received a reply yet. Any information about the status would be appreciated. Thank you.

I submitted my iOS app (Apple ID 6792378109) on 07/18/26. It has been in "Waiting for Review" for 10 days now. I did reach out to Developer Support via email on 07/26 (Case ID 20000120078126) and haven't received a reply as yet. This is a first time app submission. If the following is no longer true, it should probably be updated or changed to reflect the current situation: On average, 50 percent of apps are reviewed in 24 hours and over 90 percent are reviewed in 48 hours. Once we've completed the review, your app's status will be updated and you will be notified. in order to manage expectations. If there's an ongoing technical issue, knowing that's the cause of delays is preferable to silence. In any event, if someone is able to shake my review loose, I'd appreciate it!

My app has been waiting for review since June 13 and has been under review since June 19. I would like to know if this is considered normal. I have already sent emails to Apple requesting a faster review and asking for an explanation regarding the delay, but I have not received a helpful response. The app is called "Piscineiros." Could any fellow developers please check if this review timeline is normal or share if you've experienced something similar? Any advice would be greatly appreciated.

Hello, My app MGY Fit (Apple ID: 6793196121, iOS, version 1.0.0, build 11) was submitted for review on July 23, 2026 and has remained in "Waiting for Review" ever since. It has never moved to "In Review". There are no messages in the Resolution Center and I have not received any request for additional information. Export compliance, content rights, and advertising identifier questions were all answered at submission, and the Review Notes include demo account credentials and steps to reach the main flows. This is the first submission for this app and for my developer account, so I understand a longer wait is expected. I wanted to check whether the submission may have been routed in a way that needs attention, or whether this is simply current queue volume. Any guidance would be appreciated. Thank you.

Hello Apple Developer Community and App Review Team, I received a Pending Termination Notice regarding Section 4.3 (Spam) for my games (Scream Bird and Hopscotch). I submitted a formal appeal 7 days ago detailing the technical context, but I have not yet received an automated confirmation email or a case tracking number. Full Context of My Situation: I had previously published a game called "Scream Bird" on this account, and that was the first time I received a 4.3 Spam error. It was the first time I'd encountered this error, as all my games and applications are designed by me, from the buttons to the characters and gameplay. When I received that error, I tried to understand and modify my game a bit, thinking it might have overlapped with an existing game. But that build continued to receive the 4.3 Spam error. This time, I really didn't know what to do. I intended to keep the gameplay but redesign everything. Strangely, while I was trying to redesign and change my game, I received an email saying that Apple was reviewing my app (the one that had just been rejected), and just minutes later, my game was approved and ready for distribution. This was the first time I'd encountered something like this. I thought the review team had re-evaluated my game and changed their minds. And since the game was approved, I didn't know what else to do and just continued working on other projects. Shortly after, Google AdMob approved it (because the game was already live on the store), so ads started appearing on the game (I think this was the issue, causing the system to automatically think my game had been flagged for content changes, but the content was already there; it was just that I had set a production ID for the ads at the time, so they weren't showing – that was partly my fault). But the problems didn't end there. Recently, I published a new game called "Hopscotch" and encountered the 4.3 Spam issue again. It was then that I really looked back at the binary files I built for my games and was shocked to realize that this might be the reason the automated system incorrectly flagged my games as spam. Technical Explanation (Godot Framework & Shared Native Libraries): I build all my games myself using Godot (3.x and 4.x). Regardless of the version, I write supporting libraries (mainly to call simple native features). Therefore, all my games will have files like: notch.a, share.a, haptics.a, local-notification.a, inappstore.a... You can check it out on my GitHub page; most of it is public. https://github.com/kyoz/godot-notch https://github.com/kyoz/godot-share https://github.com/kyoz/godot-local-notification https://github.com/kyoz/godot-haptics https://github.com/kyoz/godot-leaderboard https://github.com/kyoz/godot-native-rating https://github.com/kyoz/godot-flashlight etc... However, the entire game, from images, models, scenes... almost everything I designed myself, was packed into a single [game].pck file by Godot. This makes my Godot-built games look very similar in terms of binary, but in terms of content and gameplay, they are completely unrelated. My Commitment: I've been on my Apple journey for over five years now, and I've published 20 apps/games. The journey so far hasn't been easy. But I promise I've always complied with Apple's policies. I have never engaged in subscription scams, fake reviews, bait-and-switch tactics, or any of the fraudulent conduct described in the termination notice. I am respectfully requesting: Confirmation if my appeal submitted 7 days ago is actively under review by the App Review Board. A status update or Case Reference Number for tracking. I am fully cooperative and ready to provide full source code, Godot project files, or any documentation needed. Thank you so much for your time and assistance! Best regards, Phan Minh Cuong